Problem

The /guide/features/palettes page rated poorly for being confusing. Root causes, all in the interactive explorer at the top of the page:

1. Copy Config emitted dead code. onExport produced a colors block where every line was commented out — pasting it gave a theme with no colors (silent no-op). The click path was worse: bare token strings with no role key, invalid once uncommented.
2. No visible selection state. Clicking swatches quietly accumulated into the export, but nothing on screen showed what you'd picked, which role each mapped to, or how to reset — so idle exploring silently polluted the output.
3. "Material" meant two things — the explorer's static entry vs the Material generator section lower down.
4. Static-vs-generator and the {palette.…} token syntax were never framed before the widget.

Changes

Export

• onExport now emits real, uncommented config. Clicked swatches map to theme roles (primary, secondary, …) in click order; the no-click default seeds primary/secondary from hues that actually exist in the selected palette (the old default hardcoded blue.500/slate.600, absent outside Tailwind).

Selection state

• Summary chip row below the grid: each pick shows its swatch color, mapped role, and token path, with a per-chip remove and a Clear button.
• Selected swatches get an inset outline so the grid and the export stay in sync.

Framing

• Prose above the explorer: static vs generator forms, the token-reference syntax with a link to Theming, and a note that shade-heavy palettes (Material) render transposed.
• In-widget hint explaining click-to-copy → Copy Config.
• Static Material entry relabeled Material 3 to disambiguate from the generator section.

Verification

• Export code-gen validated in isolation — no-click and multi-click branches both produce valid, resolvable config.
• vue-tsc on apps/docs: 0 errors. ESLint clean. AppCloseButton confirmed auto-registered.
• Not driven in a live browser — the docs dev server won't boot in this worktree (a build plugin's fs.watch hits ENOSPC on WSL, unrelated to this change). The interactive additions are straightforward reactive-Map bindings, but a click-through before merge is still worth doing.